The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point in your pull request via creating an issue comment (i.e. comment on the pull request page) using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

src/main/resources/messages_ko.properties (1)

33-33: Remove extra space before colon in “바로가기 :”

-유의사항 바로가기 : https://www.mosuedu.com/warning
+유의사항 바로가기: https://www.mosuedu.com/warning

src/main/resources/messages_ko.properties (2)

19-25: Comma spacing consistency (전, …)

Elsewhere in this file, there’s no space after the comma in “전,”. Align this line to match for consistency.

-시험 1주일 전, 시험 관련 유의사항과 수험표 안내 리마인드 알림이 발송될 예정입니다.
+시험 1주일 전,시험 관련 유의사항과 수험표 안내 리마인드 알림이 발송될 예정입니다.

---

32-32: Comma spacing consistency (전, …)

Same nitpick here: remove the space after the comma.

-시험 1주일 전, 시험 관련 유의사항과 수험표 안내 리마인드 알림이 발송될 예정입니다.\n\n\
+시험 1주일 전,시험 관련 유의사항과 수험표 안내 리마인드 알림이 발송될 예정입니다.\n\n\

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

src/main/java/life/mosu/mosuserver/application/notify/dto/ApplicationGuestNotifyRequest.java (3)

31-33: Use a human-readable button label instead of the URL

Using the URL string for both label and URL will render an unfriendly label. Prefer a descriptive label.

Apply:

-        return LunaNotificationButtonUrls.of(
-                NotificationButtonUrl.of(WARNING_PAGE, WARNING_PAGE)
-        );
+        return LunaNotificationButtonUrls.of(
+                NotificationButtonUrl.of("유의사항 확인", WARNING_PAGE)
+        );

---

40-41: Confirm date format expected by templates; consider explicit formatter

ISO date via LocalDate.toString() may not match the desired user-facing format.

Apply:

-                "examDate", examDate.toString(),
+                "examDate", examDate.format(DATE_FORMAT),

Add the following outside this hunk:

import java.time.format.DateTimeFormatter;

// inside record (static field)
private static final DateTimeFormatter DATE_FORMAT = DateTimeFormatter.ofPattern("yyyy.MM.dd");

---

23-27: Harden lunch mapping against null/blank lunch names

If lunch is checked but lunchName is null/blank, the template will get a null or empty value. Default to "선택 안 함" in that case.

Apply:

-        return new ApplicationGuestNotifyRequest(examApplication.paymentKey(),
-                examApplication.examDate(), examApplication.schoolName(),
-                examApplication.isLunchChecked() ? examApplication.lunchName()
-                        : "선택 안 함");
+        String lunch = (examApplication.isLunchChecked()
+                && examApplication.lunchName() != null
+                && !examApplication.lunchName().isBlank())
+                ? examApplication.lunchName()
+                : "선택 안 함";
+        return new ApplicationGuestNotifyRequest(
+                examApplication.paymentKey(),
+                examApplication.examDate(),
+                examApplication.schoolName(),
+                lunch
+        );

src/main/java/life/mosu/mosuserver/application/notify/NotifyVariableFactory.java (1)

87-93: Reduce duplication between application and guest variable builders

Both methods fetch the same projection with identical error handling. Extract a shared helper to keep DRY.

Apply within this method:

-        ExamApplicationNotifyProjection projection = examApplicationRepository.findExamAndPaymentByExamApplicationId(
-                        targetId)
-                .orElseThrow(
-                        () -> new CustomRuntimeException(ErrorCode.EXAM_APPLICATION_NOT_FOUND));
+        ExamApplicationNotifyProjection projection = loadExamApplication(targetId);
         return ApplicationGuestNotifyRequest.from(projection);

Add this helper (outside the selected range):

private ExamApplicationNotifyProjection loadExamApplication(Long targetId) {
    return examApplicationRepository.findExamAndPaymentByExamApplicationId(targetId)
            .orElseThrow(() -> new CustomRuntimeException(ErrorCode.EXAM_APPLICATION_NOT_FOUND));
}

Optionally update createApplicationVariable(...) to use loadExamApplication(targetId) as well.

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro